System and method of user interface for audio device

ABSTRACT

The disclosure provides for an audio accessory that includes earbuds or earphones, an input device, and a processor. The input device includes a first button and optionally includes additional buttons or touch sensors. The processor is configured to initiate an action when a first input is received at the first button, provide audio updates when a second input is received at the first button, and prepare the input device to receive audio input when a third input is received at the first button. Also, the processor is configured to silence a currently playing audio message and initiate playing a next audio message when a fourth input is received at one of the buttons or the touch sensors, and silence and mark the currently playing audio message for no further playback when a fifth input is received at one of the buttons or the touch sensors.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a national phase entry under 35 U.S.C. § 371of International Application No. PCT/US2017/062780, filed Nov. 21, 2017,which claims the benefit of the filing date of U.S. ProvisionalApplication No. 62/427,003, filed Nov. 28, 2016, entitled SYSTEM ANDMETHOD OF USER INTERFACE FOR AUDIO DEVICE, the disclosures of which arehereby incorporated herein by reference.

BACKGROUND

Audio accessories, such as ear buds and headsets, are commonly used withmobile computing devices to allow for hands-free use of a mobile device.Such audio accessories can be wirelessly connected or directly connectedto the mobile computing devices through wires extending from the earbuds or headset. Improved methods and devices are needed to improve auser's ability to more easily communicate with the mobile computingdevice.

BRIEF SUMMARY

Aspects of the disclosure provides for a user interface for an audiodevice that allows for a compact and intuitive way to provideinstructions to one or more computing devices. The audio device includesa positive control and hush control that receives a variety of userinput. Using these controls, a variety of tactile input may be receivedat the audio device for controlling the one or more computing devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional diagram of example systems in accordance withaspects of the disclosure.

FIG. 2 a pictorial diagram of the example systems of FIG. 1 inaccordance with aspects of the disclosure.

FIGS. 3A-3C are pictorial diagrams of example audio devices inaccordance with aspects of the disclosure.

FIG. 4 shows zoomed-in views of example input devices of the exampleaudio devices of FIGS. 3A-3B in accordance with aspects of thedisclosure.

FIG. 5 shows an example operation of the example input devices of FIG. 4in accordance with aspects of the disclosure.

FIG. 6 shows another example operation of the example input devices ofFIG. 4 in accordance with aspects of the disclosure.

FIG. 7 shows further example operation of the example input devices ofFIG. 4 in accordance with aspects of the disclosure.

FIG. 8 shows yet another example operation of the example input devicesof FIG. 4 in accordance with aspects of the disclosure.

FIG. 9 illustrates an example flow diagram in accordance with aspects ofthe disclosure.

FIG. 10 illustrates another example flow diagram in accordance withaspects of the disclosure.

DETAILED DESCRIPTION

Example Systems

FIGS. 1 and 2 include example systems 100A and 100B in which thefeatures described herein may be implemented. It should not beconsidered as limiting the scope of the disclosure or usefulness of thefeatures described herein. In this example, system 100 can includecomputing devices 110, 120, 130, 140. Each of the computing devices 110,120, 130, 140 can contain one or more processors 112 and memory 114(reference numbers depicted only within computing device 110 forsimplicity) as well as various other components as discussed below.

Memory 114 of the computing devices 110, 120, 130, 140 can storeinformation accessible by the one or more processors 112, includinginstructions 116 that can be executed by the one or more processors 112.Memory can also include data 118 that can be retrieved, manipulated orstored by the processor. The memory can be of any non-transitory typecapable of storing information accessible by the processor, such as ahard-drive, memory card, ROM, RAM, DVD, CD-ROM, write-capable, andread-only memories.

The instructions 116 can be any set of instructions to be executeddirectly, such as machine code, or indirectly, such as scripts, by theone or more processors. In that regard, the terms “instructions,”“application,” “steps” and “programs” can be used interchangeablyherein. The instructions can be stored in object code format for directprocessing by a processor, or in any other computing device languageincluding scripts or collections of independent source code modules thatare interpreted on demand or compiled in advance. Functions, methods androutines of the instructions are explained in more detail below.

Data 118 can be retrieved, stored or modified by the one or moreprocessors 112 in accordance with the instructions 116. For instance,although the subject matter described herein is not limited by anyparticular data structure, the data can be stored in computer registers,in a relational database as a table having many different fields andrecords, or XML documents. The data can also be formatted in anycomputing device-readable format such as, but not limited to, binaryvalues, ASCII or Unicode. Moreover, the data can comprise anyinformation sufficient to identify the relevant information, such asnumbers, descriptive text, proprietary codes, pointers, references todata stored in other memories such as at other network locations, orinformation that is used by a function to calculate the relevant data.

The one or more processors 112 can be any conventional processors, suchas a commercially available CPU. Alternatively, the processors can bededicated components such as an application specific integrated circuit(“ASIC”) or other hardware-based processor. Although not necessary, oneor more of computing devices 110 may include specialized hardwarecomponents to perform specific computing processes, such as decodingvideo, matching video frames with images, distorting videos, encodingdistorted videos, etc. faster or more efficiently.

Although FIG. 1 functionally illustrates the processor, memory, andother elements of computing devices 110, 120, 130, 140 as being withinthe same block, the processor, computer, computing device, or memory canactually comprise multiple processors, computers, computing devices, ormemories that may or may not be stored within the same physical housing.For example, the memory can be a hard drive or other storage medialocated in housings different from that of the computing devices 110,120, 130, 140. Accordingly, references to a processor, computer,computing device, or memory will be understood to include references toa collection of processors, computers, computing devices, or memoriesthat may or may not operate in parallel.

Each computing device 110, 120, 130, 140 may be a mobile computingdevice capable of wirelessly exchanging data with a server over anetwork such as the Internet. For instance, client computing device 110may be a device such as a mobile phone, wireless-enabled PDA, a tabletPC, or a netbook. Client computing device 120 may be a full a full-sizedpersonal computing device. The client computing devices 110 and 120 mayhave all of the components normally used in connection with a personalcomputing device such as processors and memory discussed above as wellas a display such as displays 122 or 152 (e.g., a touch-screen, aprojector, a television, a monitor having a screen, or other device thatis operable to display information), and user input device 124 or 154(e.g., a mouse, keyboard, touch-screen or microphone). The clientcomputing device 110 and 120 may also include connection components 126or 156 (shown only in FIG. 1) that facilitate wired, such as via a jack,or wireless connections 127 or 157, such as via WiFi or Bluetoothprotocols, with audio accessories 130, 140. The client computing devicemay also include a camera for recording video streams, speakers, anetwork interface device, and all of the components used for connectingthese elements to one another.

Computing devices 130 and 140 may be audio accessory devices configuredto communicate via wired or wireless connection 127, 157 with one ormore of client computing devices 110 or 120. For instance the audioaccessory device 130 may include one or more speakers 132 includingearphones or earbuds for generating sound, a user an input device 134 toallow a user to input instructions to the audio accessory device andalso computing device 110 as discussed below, and a connection component136, such as an audio jack, for mating with an audio port of computingdevice 110 (not shown). Similarly, the audio accessory device 140 mayinclude one or more speakers 142 including earphones or earbuds forgenerating sound, a user an input device 144 to allow a user to inputinstructions to the audio accessory device and also computing device 110as discussed below, and a connection member 146, such as a wirelesstransmitter and receiver, for wirelessly communicating information tothe processor of computing device 120.

Example Audio Accessories

An audio accessory 300, corresponding to either audio accessory 130 or140, as shown in FIG. 3A, includes a pair of ear phones or ear buds 302(corresponding to speakers 132 or 142) attached to a respective earhooks 304 with a wire 306 respectively extending from one ear hook tothe other, as well as an input device 308 (corresponding to input device134 or 144) with a sliding button 310. Ear hooks 304 are configured tofit behind user's ears when ear phones or ear buds 302 are worn inuser's ears. Wire 306 is configured to hang behind a user's head, neck,or shoulders when earphones or ear buds 32 are worn in user's ears. Theinput device 308 is positioned along one of the ear hooks 304 andprovides a user with the ability to communicate (directly or indirectly)with a client computing device, such as client computing devices 110 or120, using tactile inputs (clicks and/or sliding) or a combination ofvoice and tactile inputs. Sliding button 310 is configured to slide inone direction from a resting position along ear hook 302. Volumecontrols 312 are positioned along an opposite ear hook 304 and includesvolume up and volume down buttons.

An audio accessory 320, corresponding to either audio accessory 130 or140, as shown in FIG. 3A, includes a pair of ear phones or ear buds 322(corresponding to speakers 132 or 142) attached to respective wires 324that connect to respective ends of a U-shaped band 326, as well as aninput device 328 (corresponding to input device 134 or 144) with abutton 330 and touch sensors (not shown) disposed on two sides of button330. Band 326 is configured to sit around a user's neck when ear phonesor ear buds 322 are worn in user's ears. Wires 324 are configured tohang down from user's ears when earphones or ear buds 32 are worn inuser's ears. The input device 328 is positioned along one of the arms ofband 326 and provides a user with the ability to communicate (directlyor indirectly) with a client computing device, such as client computingdevices 110 or 120, using tactile inputs or a combination of voice andtactile inputs. Volume controls 332 are positioned along an opposite armof band 326 and includes volume up and volume down buttons.

Audio accessory 340, corresponding to either audio accessory 130 or 140,as shown in FIG. 3A, also includes ear phones or ear buds 322, wires324, band 326, input device 342, and volume controls 332. Input device342 has sliding button 344 that is configured to slide in two directionsfrom a resting position along the arm of band 326.

An audio accessory 360, corresponding to either audio accessory 130 or140, as shown in FIG. 3B, includes a pair of ear phones 362(corresponding to speakers 132 or 142) attached to respective ends of agenerally C- or U-shaped band 364, as well as an input device 366(corresponding to input device 134 or 144) with a buttons 368, 370, 372.Band 326 is configured to fit around and over a portion of a user's headwhen ear phones 362 are worn on user's ears. The input device 366 ispositioned on an outer housing of one of the ear phones 362 and providesa user with the ability to communicate (directly or indirectly) with aclient computing device, such as client computing devices 110 or 120,using tactile inputs or a combination of voice and tactile inputs.Volume controls 374 are positioned on an outer housing of an oppositeear phone 362 and include volume up and volume down buttons.

An audio accessory 380, corresponding to either audio accessory 130 or140, as shown in FIG. 3B, includes a pair of wireless ear buds 382(corresponding to speakers 132 or 142) having a housing 384 with outersurfaces 386, as well as an input devices 387 (corresponding to inputdevice 134 or 144) with touch sensors (not shown). The touch sensors maybe positioned on the outer surfaces 386 to form buttons 388, 389.Housing 384 is configured to have outer surface 386 facing outward andsubstantially parallel to a user's ear lobe when ear buds 382 are wornin user's ears. Volume controls are not included in audio accessory 380.

The input devices 308, 328, 342, 366, 387, which are illustrated in FIG.4, are shown as being a part of ear phones or ear buds, ear hooks, orbands, but in other examples, the input device may be a separate andstandalone audio accessory that wirelessly communicates with one or moreother audio accessories. As shown, for example, in FIG. 3B, the audioaccessory 390 may be similar to audio accessory 130 or 140, having inputdevice 392 with sliding button 394. Sliding button 394 is configured toslide in one direction from a resting position along a channel 396.Although not necessary, in some instances, audio accessory 390 may notinclude speaker 132 or be physically connected to speaker 132. Audioaccessory 390 can wirelessly communicate with one or more other audioaccessories, including wireless earbuds, a wireless speaker 260(corresponding to speakers 132), or speaker 128 of computing device 110.Audio accessory 390 can provide a user with a convenient way tocommunicate with another audio accessory or a computing device 110. Dueto its size, the audio accessory 390 can be placed in the pocket of auser, clipped to the clothing of a user, or stored in any otherconvenient user location.

An input device, such as input device 308 shown in FIG. 3C, may includean outer housing 301, an elongated channel 303, and a sliding button 310disposed within the elongated channel 303. The input device may allow auser to communicate with a computing device, such as computing device110 or 120. For instance, user input may be sent directly to theprocessors in the computing devices 110 or 120 or to indirectly to theprocessors within the input device that provide instructions to thecomputing devices 110 or 120.

The outer housing, such as outer housing 301, may have variousconfigurations. The outer housing 301 may include an interior basesurface 305, an exterior base surface 307, an outer top surface 309, aninterior top surface 311, a first end 313 and a second end 314 that isopposite the first end 313. The channel, such as channel 303, may have achannel opening that extends along a majority of the length of the outertop surface of the outer housing. The outer housing can enclose aninterior space configured to house various components of the inputdevice, such as component 315. The outer housing may be comprised of anynumber of materials, including a plastic resin.

The overall shape of the outer housing may be oblong with rounded edges,such as the shape of the outer housing 301, but in other examples, theshape may vary. For example, the outer housing may alternatively be inthe shape of a rectangle or a square. The outer housing may be comprisedof any number of materials, including a plastic resin.

Electronic components, such as component 315, may be disposed within theinterior of the outer housing. A printed circuit board, for example, maybe positioned adjacent the interior base surface. The printed circuitboard can include circuitry necessary for the input device tocommunicate with the computing devices 110 or 120. The printed circuitboard may be a flat and rigid board, but other types of circuit boards,such as flexible circuit boards, can be utilized. A first circuit boardcontact and a second circuit board contact may be disposed along theouter surface of the printed circuit board.

As with the outer housing, the sliding button may have variousconfigurations and may be comprised of any number of materials,including a plastic resin. The sliding button, such as the slidingbutton 310, may be u-shaped and include an interior arm joined with anexterior arm by a neck.

The exterior arm can overlie the top surface of the housing. Exteriorarm can include an outer contact surface configured to receive a fingerof a user and to allow a user to operate the sliding button. In oneexample, the outer surface can be contoured to the shape of a finger orinclude surface dimpling, knurling, or roughenings to facilitate use ofthe sliding button by a user's finger. An interior contact surface ofthe exterior arm may be spaced away from the outer top surface of theouter housing by a distance X, which provides the clearance needed forthe sliding button to move in a vertical direction between the top andbottom surfaces of the housing.

The interior arm may be an elongated arm positioned within the interiorportion of the outer housing. A button contact facing toward theinterior base surface of the housing may be provided at one end of theinterior arm. Button tabs may extend from the neck and a magnet may beprovided adjacent the button tabs, or alternatively, within the one orboth button tabs biasing element, which can include, for example, aspring, may be positioned at or near the second end of the interior arm.As shown, the spring may be provided around at least a portion of theinterior arm to bias the interior arm and the sliding button toward thefirst end of the channel.

The sliding button may be configured to move along the channel between aresting position adjacent a first end of the channel and a actuatedposition adjacent a second end of the channel. The channel may have achannel opening extending across the top surface, as well as a width Wextending between channel sidewalls. The neck of the sliding button maybe sized to fit within the channel opening. The button tabs extendingaway from the neck and toward the channel sidewalls may be sized to fitwithin the channel.

A position sensor may also be provided on one or both channel sidewalls.In one example, the position sensor is a hall sensor, but other types ofposition sensors may additionally or alternatively be used.

The sliding button 308 as shown in FIGS. 3C, 4, and 5 is in an exampleresting position or “stationary” position. In the resting position, thesliding button is positioned adjacent first end of the channel andadjacent the first end of the housing due to the biasing force of thespring. In other words, the spring biases the button towards the firstend so that the button is at rest in the resting position. In thisposition, the button contact of the first interior arm can also directlyoverlie the first contact on the printed circuit board while in thestationary position.

To move into an actuated position, the sliding button 308 as shown inFIGS. 6 and 7 is configured to move within the channel between the firstend and second end of the housing, as well as between the first end andthe second end of the channel A force F can be applied to the slidingbutton in a direction that is towards the second end of the channel or adirection which is opposite of the biasing force of the spring, so as toovercome the biasing force of the spring towards the first end of thechannel. The button tabs extending from the neck of the sliding buttoncan guide the sliding button along the channel. The sliding button canbe moved from the resting position, at the first end of the channel,along the channel towards the second end of the channel. The slidingbutton continues to move along the channel until the sliding buttonreaches the second end of the channel.

In one example, the actuated position, as shown in FIGS. 6 and 7, isreached when the button tabs contact the second end of the channel. Asthe sliding button slides along the channel, the interior arm compressesthe spring. The spring will continue to compress until the slidingbutton is positioned adjacent the second end of the channel.

In the actuated position, the spring will continue to bias the slidingbutton towards the resting position. Thus, when the force F is releasedor removed, the sliding button will return to the resting position.

As noted above, the input device may also include a position sensor todetect movement of the sliding button along the channel. When thesliding button is moved from the resting position at the first end ofthe channel toward the second end of the channel into the actuatedposition, the position sensor will detect the change in position of themagnet in the neck. In other words, the distance between the magnet andthe position sensor will be different when the sliding button is in theresting position and when the sliding button is in the actuatedposition. In this regard, the magnet will also have a resting positionand a second activated position corresponding to the resting positionand the second active position. Upon detection of a change in a positionof the magnet from the resting position to the second activated positionof the magnet by the position sensor, the position sensor will emit asignal indicating movement of the sliding button into the actuatedposition.

The signal can be received by processors within the input device thatwill send instructions to the computing device 110 or 120 to perform afirst pre-determined command or function, such as canceling orinitiating a particular action being performed by the computing device110 or 120. Alternatively, the signal can be directly received byprocessors within the computing device 110 or 120.

The sliding button may be further depressed in the resting position, aswell as in the actuated position, to initiate an action by the clientcomputing device 110 or 120. As shown in the example of FIG. 5, when thesliding button is in the resting position, the sliding button can bedepressed in a vertical or y-direction relative to the outer top surfaceof the outer housing. The depression of the sliding buttons 310 and 344are illustrated in FIG. 5 as an asterisk. Movement of the sliding buttonin the y-direction causes the button tabs of the sliding button to moveinto the first vertical channel, which extends from the channel. Suchmovement further reduces the distance X between the interior contactsurface of the exterior arm and outer top surface of the input devicehousing so that the interior surface is directly adjacent top surface.Button contact on the sliding button can then make contact with thecircuit board contacts of the printed circuit board. When the buttoncontact contacts the first circuit board contact, a signal can begenerated by the circuit board that will instruct the client computingdevice 110 or 120 to perform a second pre-determined function. Forexample, the signal may instruct the client computing device 110 or 120to initiate a voice command prompt.

Similarly, when the sliding button is in the actuated position, such asthe sliding buttons 310 and 344 shown in FIGS. 6 and 7, the buttoncontact 260 can overlie the second board contact on the printed circuitboard. In the actuated position, the sliding button can also bedepressed in a vertical or y-direction relative to the outer top surfaceof the outer housing. When moved in the vertical direction, the buttoncontact can make contact with the second circuit board contact of theprinted circuit board. A signal can be generated by processors in theprinted circuit board that will be received by the client computingdevice 110 or 120 to perform a pre-determined function. For example,when in the actuated position, a signal can be generated that instructsthe client computing device 110 or 120 to close an application currentlyrunning on the client computing device or some other activity currentlybeing executed by the client computing device.

In some implementations, the sliding button, such as in sliding button344 shown in FIG. 8, may be biased at a position between the first endand the second end of the channel. In addition to being configured tomove to a first actuated position shown in FIGS. 6 and 7, the slidingbutton may also be configured to move to a second actuated position bysliding in the opposite direction than the first actuated position. Thebutton contact may overlie a third circuit board contact on the printedcircuit board when the sliding button is in the second actuatedposition. The sliding button may also be depressed in a vertical ory-direction relative to the outer top surface of the outer housing inthe second actuated position, such that the button contact makes contactwith the third circuit board contact. A signal can be generated byprocessors in the printed circuit board that will be received by theclient computing device 110 or 120 to perform a pre-determined function.

Prolonged depression of the sliding button can initiate yet otherpre-determined functions that are to be performed by the clientcomputing device 110 or 120. By way of one example, holding the slidingbutton depressed for a prolonged period of time causes the buttoncontact to be in contact with the first circuit button contact, secondcircuit board contact, or third circuit board contact for an extendedperiod of time. The extended period of time may be any pre-set period oftime, such as two or more seconds. In one example, prolonged depressionof the button while in the resting position places the button contact incontact with the first circuit board contact for a prolonged period oftime. This prolonged depression can initiate, for example, a voicecommand mode of the client computing device. Similarly, prolongeddepression of the button while in the actuated position places thebutton contact in contact with the second circuit board contact for anextended period of time. This prolonged depression can also initiate,for example, a voice command mode of the client computing device 110 or120.

Rapid successive movement of the sliding button can also initiate otherpre-determined functions at the client computing device 110 or 120. Forexample, rapid successive movement of the sliding button in a verticalor y-direction relative to the top surface of housing while in theresting position or the second stationary position can be used to“click” the button and initiate still other functions. In the restingposition, the button contact will rapidly contact the first circuitboard. Similarly, in the actuated position, the button contact willrapidly contact the second circuit board contact. The processors can bepre-programmed to recognize the multiple clicks as a particular commandor function and send pre-determined signals to the client computingdevice 110 or 120 based on the number and location (first circuit boardcontact or second circuit board contact).

In another example, rather than the button contact of the sliding buttondirectly contacting the first and second circuit board contacts, one ormore additional position sensors may be provided within or adjacent thevertical channel in the input device to detect vertical movement of thebutton in the y direction along the vertical channel. The positionsensors can, for example, detect the magnet in the neck of the slidingbutton. Detection of vertical movement can send signals and instructionsdirectly or indirectly to the mobile phone to perform a pre-determinedfunction.

As noted above, the input device can be configured to allow a user toprovide tactile input to the electronic device to perform a particularfunction. For example, the input device can be used to initiate anaction or discontinue an action or function based on the position of thebutton at a certain location, as well as the depression of the button ata particular location.

In one example, the input device initiates an action when the slidingbutton is used as follows: (1) sliding button is depressed in theresting position; (2) sliding button is depressed and held down in theresting position; (3) sliding button is depressed sequentially two ormore times; (4) a button or touch sensor is contacted.

The input device can further cancel or discontinue an action orapplication when the button is used as follows: (1) sliding button isslid from the resting position to an actuated position; (2) slidingbutton is slid from the resting position to an actuated position andfurther depressed in the actuated position; (3) sliding button is slidfrom the resting position to an actuated positioned and depressed in theactuated position for a prolonged time period; (4) a second button ortouch sensor is contacted.

In another example, the sliding button can be used to first cancel andthen initiate another function when the sliding button is slid from theresting position to the actuated position, and then sequentiallydepressed in the second stationary position at least two or more timesor held down for a prolonged period of time.

Other hardware can be used to support a click and slide motion, as wellas other user input gestures noted herein. For instance, the inputdevice of the audio device may additionally or alternatively includetouch-based and/or pressure sensitive input, including touch-basedand/or pressure sensitive sensors and circuitry. Touch-sensitive and/orpressure sensitive circuitry and sensors may be disposed within thehousing such that at least a portion of the outer wall of the housing isconfigured as a touch-based and/or pressure sensitive input surface. Auser may, for example, tap the touch based and/or pressure sensitiveinput surface or hold a finger for a prolonged period of time, insteadof clicking or holding down the button. Additionally, a user may slide afinger across a length of the touch and/or pressure input surface tocancel an action, instead of sliding a button.

Example Methods

As noted above, the input device can be used to initiate and cancel ordiscontinue an action being performed by the client computing device 110or 120. Positive controls associated with initiating an action areincluded in the input device. Positive controls include play/pause,fetching updates from a personal itinerary, confirming actions, turningon the microphone for audio input, etc. One or more buttons of the inputdevice may be used to provide user input. For example, clicking a buttonof the input device, as shown by the asterisk in FIG. 5, may turn onmusic. When provided with an option for an action, the one or moreprocessors may provide for a length of time for a user to respond. Anexample of options may be “You have a meeting at 4:00 pm. It is now 4:30pm. Would you like another reminder at 4:45 pm?” or “You have 4 newmessages. Would you like to hear them?” In these instances, the buttonmay also be clicked once as the user response to initiate the action inthe provided option.

The one or more buttons may also be double-clicked to provide adifferent user input. Double-clicking the buttons indicated in FIG. 5,for example, may request an audio update from an itinerary or storedmessages, regardless of what action is being performed by the one ormore processors at the time.

In addition, the one or more buttons may be pressed down and held torequest a different action than clicking or double-clicking. Forexample, pressing and holding one of the buttons indicated in FIG. 5 mayopen the microphone for a user to provide audio input to the one or moreprocessors. The audio input may be commands that may be parsed by theone or more processors as actions to perform, or may be audio messagesto be sent by the one or more processors.

Hush controls associated with canceling or discontinuing an action beingperformed by client computing device 110 or 120 is included in the inputdevice. The hush control gesture is distinct from the positive controlgesture. Rather than a clicking gesture, the hush control gesturecomprises a slide or a squeeze, which are more related to an act ofdismissing an action or muffling a sound. In other examples where theinput device does not have a sliding button or touch sensors located onthe sides of an input device, the gesture for the hush control may bepressing a different button than the positive control. Hush controls areuseful to quickly dismiss any incoming messages or reminders that areunnecessary or disruptive to the user. For example, the computing device110 or 120 may receive a text message and automatically initiate readingof the text message via an audio accessory. As shown in FIG. 6, the textmessage reading may be stopped by sliding a button in the input deviceor squeezing the sides of the input device where touch sensors arelocated.

As shown in FIG. 7, hush controls may also be used to skip through alist of items, such as messages, music tracks, or radio stations. Forexample, a user may double-click a button to receive updates from storedmessages, and as messages are being read, the hush control may beperformed to skip to a next message in the list of stored messages. Whenlistening to music or podcasts, the hush control may be used to skip toa next track in the list.

A variation of the hush control may be used to skip at a higher level ora fast forward action. The variation may be a slide and hold or squeezeand hold gesture. The one or more processors may detect theslide/squeeze and hold gesture by detecting constant pressure on theinput device and determine a length of time the pressure is held. Aftera predetermined amount of time, the one or more processors may performthe higher level skip or fast forward. For example, a higher level skipmay be skipping through different podcasts rather than tracks within thesame podcast or skipping through different albums rather than trackswithin the same album. The slide/squeeze and hold gesture may also beused for a fast forward action and may jump forward in time of a musicaltrack, for example, for a set amount of time.

In the context of updates and messages, the variation of the hushcontrol may be used to permanently silence certain updates and messages.While the hush control may skip the update or message being read at themoment to be read at a later time, the variation of the hush control maycause the update or message to be skipped and marked for no futurereading.

In some examples, the skip control may be a separate button on the inputdevice.

Some input devices may also include a previous control, as shown in FIG.8. The previous control may be a separate button from the positivecontrol and the skip control. In other examples may be a slide gesturein an opposite direction of the hush/skip slide gesture. The previouscontrol is useful in navigating back to re-listen to a music track ormessage. When the previous control is repeated one or more times, theone or more processor may navigate to a previous music track or message.When the previous control is held for a predetermined period of time,the one or more processors may navigate backwards at a higher level,such as albums or stations, or may rewind a set amount of time.

A first example workflow according to the methods described aboveincludes the following steps. A user may start a run. The clientcomputing device may detect the run activity based on informationprovided by the user, such as steps, heartbeat, location, etc. An audionotification may be played indicating that the activity has beendetected. A positive control gesture, such as pressing button 310, 330,344, 370, or 388, may be received. In response to the positive controlgesture, the client computing device may read a list of actions theclient computing device may perform and instructions to select an actionfrom the list. For example, the client computing device may provide theoption to track the run and listen to a playlist and provideinstructions to click the positive control to choose this option. Aclick may be received at the positive control as or after the option isprovided, in which case the client computing device commences trackingthe user's run and playing the playlist. An audio notification may beplayed confirming the commencement of the action.

While performing the action, another notification may be played, such asan audio notification of a received message from a particular person.The volume of the playlist may be reduced when the audio notification isplayed. The positive control may be clicked as or after the audionotification for the message is played, and in response, the message isread while maintaining or further reducing the volume of the playlist.While the message is read aloud, a hush control gesture may be received,and the client computing device may stop the message. The hush controlgesture may be, for example, sliding a button, such as buttons 308 and342, from a resting position to an actuated position, squeezing an inputdevice, such as input devices 328, 366, or pressing a second buttondifferent from the button associated with the positive control, such asbutton 389. When the message is stopped, the volume of the playlist mayresume the original volume.

The client computing device may detect an end to the run activity basedon the information provided by the user, such as steps stopping,heartbeat slowing, location being near the start location, etc. When theend to the run activity is detected, the client computing device mayprovide an audio summary of the run activity. For example, the clientcomputing device may provide information related to the steps taken,distance, time elapsed, calories burned, etc.

When a sliding button is moved from a resting position to the actuatedposition and held in the actuated position while the playlist isplaying, the client computing device may cycle through a list ofstations, playlists, podcasts, or other audio experience, reciting thetitle or playing a beginning clip of each in turn. The cycle maycontinue until the sliding button is released from the actuatedposition. The audio experience whose title or clip was played prior tothe release of the sliding button may continue to play.

A second example workflow according to the methods described aboveincludes the following steps. A second positive control gesture, such asdouble-clicking button 310, 330, 344, 370, or 388, may be received. Thesecond positive control gesture may indicate a request for updates. Inresponse to the second positive control gesture, the client computingdevice may read aloud a series of updates based on time of day,location, or user preferences. For example, when the second positivecontrol gesture is received at 8:00 am, the series of updates mayinclude the time, the weather for a current location, review of voicemessages, a list of upcoming scheduled events for the day, a review ofunread emails, and news stories of the day.

When a hush or skip control gesture is received, a currently playingupdate may be stopped, and a next update may be played. The hush or skipcontrol gesture may be, for example, sliding button 310, 344 to a firstactuated position, squeezing input devices 328, 366, or pressing asecond button 372, 389 different from the button associated with thesecond positive control gesture. For example, the weather for thecurrent location is played until the hush control gesture is received,at which point the client computing device may stop playing the weatherand start playing the review of voice messages.

A previous control gesture, such as sliding button 344 upwards to asecond actuated position or pressing a third button 368, may be receivedas an update is played and cause the update to be played from thebeginning. For example, as the review of voice messages plays, theprevious control gesture may be received. In the response, the currentlyplayed voice message may be played from the beginning.

When an update ends either by receiving a hush or skip control gestureor by completing the update, the next update may automatically be readaloud. For example, when the review of voice messages is completed, thelist of upcoming scheduled events for the day may be played. A hush orskip control may be received while the list is played, and the clientcomputing device may start to play the review unread emails. A hush orskip control may be received as the review of unread emails, and theclient computing device may provide an option to hear the news storiesof the day. The positive control gesture, such as clicking button 310,330, 344, 370, or 388, may be received as an indication to accept theoption to play the news stories of the day, and the client computingdevice may start to play the news stories.

A positive control gesture related to providing verbal instructions tothe client computing device may be received, such as pressing andholding button 310, 330, 344, 370, or 388 for a predetermined time. Forexample, after a notification is played by the client computing devicerelated to an upcoming scheduled event, button 310, 330, 344, 370, or388 may be pressed and held for more than one second, the clientcomputing device may play a chime and prepare to receive verbalinstructions, such as by activating a microphone. After the userprovides verbal instructions, the client computing device may determinesteps to perform in relation to the instructions and confirm the stepsby playing a summary of the steps. For example, a user may say, “remindme to add the sales figured to the presentation when I get to work,” andthe client computing device may provide the audio, “got it, would youlike to save this reminder?” The user may respond by saying “yes” orproviding the positive control gesture, and the client computing devicemay provide the audio “ok, it's saved.”

At a later point in the day, while music is being played, a message maybe received at the client computing device. The music may be stopped anda notification for the message may be played, followed by an audio ofthe message, such as an audio of a voice message or a text-to-speechversion of a text message. Shortly after the message is played, such aswithin one or two seconds, the second positive control gesture may bereceived. A series of updates may be played, starting with the currenttime and followed by a replay of the message that was played just a fewsecond prior. In some implementations, the message may be played whenthere are no new updates regardless of temporal proximity to the secondpositive control gesture. A hush control variation, such as sliding andholding button 310, 344 or squeezing and holding input device 328, 366,may be received and detected by the client computing device while themessage is being replayed. In response to the hush control variation,the client computing device may stop replaying the message and eitherdelete the message or remove the message from updates. The music maythen be resumed.

A third example workflow according to the methods described aboveincludes the following steps. A song played by the client computingdevice may be nearing an end. A previous control gesture may be receivedby the client computing device while the song is still playing. Theprevious control gesture may be, for example, sliding button 344 upwardsto a second actuated position or pressing a third button 368. A firstmessage may be received at the client computing device. The music may bestopped and a notification for the message may be played, followed by anoption to listen to the first message. A positive control gesture may bereceived by the client computing device within a predetermined amount oftime in response to the option to listen to the first message. The firstmessage may be played as an audio of a voice message, a text-to-speechversion of a text message. After the first message is played, the musicmay resume where it was previously stopped. Volume for the music may beadjusted based on input from the user by using volume controls, such asvolume controls 332, 312, 372.

A second message may be received at the client computing device. Themusic may be stopped and a notification for the second message may beplayed, followed by the audio of the second message. The option tolisten to the message is not played after the first message was selectedto play. After the second message I played, the music may resume whereit was previously stopped.

At a later point in time as another song is playing, a positive controlgesture related to providing verbal instructions to the client computingdevice may be received by the client computing device, such as pressingand holding button 310, 330, 344, 370, or 388 for more than one second.In response, the client computing device may play a chime and prepare toreceive verbal instructions, such as by activating a microphone. Afterthe user provides verbal instructions, the client computing device maydetermine steps to perform in relation to the instructions and confirmthe steps by playing a summary of the steps. In this example, the verbalinstructions may be, “share this track with London crew on messagingapp.” The client computing device may determine that the steps includesending the song that was playing to the London crew group via themessaging app. Further, the client computing device may provide afurther option to send a message with the song via the messaging app.Additional verbal instructions may accept the further option and providetext of the message, such as “I can't stop listening to this track.” Theclient computing device may then send the song with the aforementionedmessage via the messaging app.

A second positive control gesture, such as double-clicking button 310,330, 344, 370, or 388, may be received to request updates at a furtherpoint in time. In response to the second positive control gesture, theclient computing device may read aloud a series of updates including thetime and a list of upcoming scheduled events for the day. An upcomingscheduled event may include a meet-up with friends indicated to be at aparticular restaurant. After the meet-up event is read aloud, anotherpositive control gesture related to providing verbal instructions to theclient computing device may be received. The verbal instructions may beto “navigate there,” where “there” is determined by the client computingdevice to be the location related to last-read event, or the particularrestaurant in this scenario. In response, the client computing devicemay determine or receive navigation instructions to the particularrestaurant, and may provide the navigation instructions as the clientcomputing device is moved through space.

As the client computing device provides navigation instructions to theparticular restaurant, a message may be received, and the clientcomputing device may play a notification of the message and the audio ofthe message. A hush control variation, such as sliding and holdingbutton 310, 344 or squeezing and holding input device 328, 366, may bereceived and detected by the client computing device while the messageis being played. In response to the hush control variation, the clientcomputing device may stop playing the message and either delete themessage or remove the message from updates. Music and/or navigationinstructions may be resumed.

FIG. 9 illustrates an example flow diagram 900 is shown in accordancewith some of the aspects described above that may be performed by theone or more processors of the audio accessories described above. WhileFIG. 9 shows blocks in a particular order, the order may be varied andthat multiple operations may be performed simultaneously. Also,operations may be added or omitted.

At block 902, an input device of an audio accessory may receive a firstpositive control gesture of a button. The first positive control gesturemay be, for example, double-clicking the button. At block 904, the oneor more processors may provide a series of audio updates in response tothe received first positive control gesture. The audio updates may beretrieved from a memory of a client computing device or received fromone or more processors of the client computing device. The one or moreprocessors may provide the series of audio updates by causing the audioupdates to be played through earbuds or earphones of the audioaccessory.

At block 906, the input device may receive a hush control gesture of thebutton when a first audio update of the series of audio updates isplaying. The hush control gesture may be, for example, sliding thebutton from a rest position to an actuated position through a channel ofthe input device. At block 908, the one or more processors may cause thefirst audio update to stop playing and initiate playing a second audioupdate of the series of audio updates in response to receiving the hushcontrol gesture. The one or more processors may cause the first audioupdate to stop playing by sending a communication to the clientcomputing device with instructions to stop playing the first audioupdate. Likewise, the communication sent to the client computing devicemay also include instructions to initiated playing the second audioupdate in the series of audio updates. The second audio update may bereceived from the client computing device and caused to play through theearbuds or earphones of the audio accessory.

At block 910, the input device may receive a previous control gesture ofthe button when the second audio update is playing. The previous controlgesture of the button may be, for example, sliding the button from therest position in an opposite direction from the actuated position to asecond actuated position through the channel of the input device. Atblock 912, the one or more processors may cause the second audio updateto be replayed from the beginning in response to receiving the previouscontrol gesture. The one or more processors may cause the second audioupdate to be replayed by sending a communication to the client computingdevice with instructions to start playing the second audio update fromthe beginning. In other implementations, the second audio update may bereplayed from a memory of the audio accessory.

At block 914, after the second audio update, the one or more processorsmay initiate playing a third audio update that provides an action optionrelated to the audio accessory. As described above, the third audioupdate may be received from the client computing device and playedthrough the earbuds or earphones of the audio accessory. The actionoption may be, for example, modifying an audio message, changing userpreferences in relation to an audio message, or initiating or stoppingan audio message. At block 916, the input device may receive a secondpositive control gesture of the button when the third audio update isplaying. The second positive control gesture may be different from thefirst positive control gesture, for example, a single click of thebutton. At block 918, the one or more processors may initiate the actionoption in response to receiving the second positive control gesture.Initiating the action option may involve sending a communication to theclient computing device with instructions to perform the action optionor may involve performing the action option at the audio accessory.

FIG. 10 illustrates another example flow diagram 1000 is shown inaccordance with some of the aspects described above that may beperformed by the one or more processors of the audio accessory. WhileFIG. 10 shows blocks in a particular order, the order may be varied andthat multiple operations may be performed simultaneously. Also,operations may be added or omitted.

At block 1000, an input device of an audio accessory may receive a firstpositive control gesture of a button that is related to receiving audioinput. The first positive control gesture may be, for example, pressingand holding the button down in a resting location for a predeterminedamount of time. At block 1004, the one or more processors may preparethe audio accessory for receiving audio input in response to the firstpositive control gesture. Preparing the audio accessory for receivingaudio input may include, for example, activating a microphone on theinput device.

At block 1006, the audio input may be received by the input device. Theaudio input may be received within a set amount of time from when thefirst positive control gesture is received, such as one or two seconds.At block 1008, the one or more processors may determine one or moresteps to perform based on parsing instructions from the received audioinput. The one or more processors may parse instructions using speechrecognition technology. In alternative implementations, the one or moreprocessors of the audio accessory may send the received audio input tothe client computing device, and the client computing device may performthe parsing and determining steps of block 1008.

At block 1010, the one or more processors of the audio accessory mayprovide an audio summary of the determined one or more steps. In someexamples, the one or more processor may receive the audio summary fromthe client computing device and cause the earbuds and earphones to playthe audio summary. At block 1012, the input device may receive a secondpositive control gesture of the button with a predetermined length oftime from providing the audio summary. The second positive controlgesture may be different from the first positive control gesture, suchas a single click of the button. At block 1014, the one or moreprocessors, may cause the determined one or more steps to be performedin response to receiving the second positive control gesture. The one ormore processors may perform the determined one or more steps or may senda communication to the client computing device with instructions for theclient computing device to perform at least one of the determined one ormore steps.

Unless otherwise stated, the foregoing alternative examples are notmutually exclusive, but may be implemented in various combinations toachieve unique advantages. As these and other variations andcombinations of the features discussed above can be utilized withoutdeparting from the subject matter defined by the claims, the foregoingdescription of the embodiments should be taken by way of illustrationrather than by way of limitation of the subject matter defined by theclaims. In addition, the provision of the examples described herein, aswell as clauses phrased as “such as,” “including” and the like, shouldnot be interpreted as limiting the subject matter of the claims to thespecific examples; rather, the examples are intended to illustrate onlyone of many possible embodiments. Further, the same reference numbers indifferent drawings can identify the same or similar elements.

The invention claimed is:
 1. An audio accessory comprising: a pair of earbuds; an input device including a button, the button being configured to slide between a resting position and an actuated position; and one or more processors operatively coupled to the pair of earbuds and the input device, the one or more processors being configured to: initiate an action when a click of the button is received by the input device; provide audio updates when a double-click of the button is received by the input device; prepare the input device to receive audio input when a prolonged click of the button is received; silence a currently playing audio message and initiate playing a next audio message through the pair of earbuds when a slide of the button to the actuated position is received by the input device; and silence the currently playing audio message and mark the currently playing audio message for no further playback when a prolonged hold of the button at the actuated position is received by the input device.
 2. The audio accessory of claim 1, wherein: the button is also configured to slide between the resting position and a second actuated position; and the one or more processors are configured to play a previous audio message when a slide of the button to the second actuated position is received.
 3. The audio accessory of claim 1, wherein when the click of the button is received after an audio message suggesting a given action has been played through the pair of earbuds, the initiated action is the given action.
 4. The audio accessory of claim 1, wherein the provided audio updates are based on one or more of time of day, location, and a user preference.
 5. The audio accessory of claim 1, wherein the one or more processors are configured to prepare the input device to receive audio input by activating a microphone of the audio accessory.
 6. The audio accessory of claim 1, wherein the one or more processors are further configured to initiate playing a previous audio message when the slide of the button to the actuated position is received by the input device and there is no additional next audio message.
 7. The audio accessory of claim 1, wherein the one or more processors are in communication with a memory of a client computing device, the memory storing one or more of the audio updates and audio messages that are configured to be played using the audio accessory.
 8. An audio accessory comprising: a pair of earbuds; an input device including a button and two touch sensors on opposite sides of the input device, the two touch sensors being positioned to either side of the button; and one or more processors operatively coupled to the pair of earbuds and the input device, the one or more processors being configured to: initiate an action when a click of the button is received by the input device; provide audio updates when a double-click of the button is received by the input device; prepare the input device to receive audio input when a prolonged click of the button is received; silence a currently playing audio message and initiate playing a next audio message through the pair of earbuds when tactile input is received at the two touch sensors of the input device; and silence the currently playing audio message and mark the currently playing audio message for no further playback when prolonged tactile input is received at the two touch sensors by the input device.
 9. The audio accessory of claim 8, wherein when the click of the button is received after an audio message suggesting a given action has been played through the pair of earbuds, the initiated action is the given action.
 10. The audio accessory of claim 8, wherein the provided audio updates are based on one or more of time of day, location, and a user preference.
 11. The audio accessory of claim 8, wherein the one or more processors are configured to prepare the input device to receive audio input by activating a microphone of the audio accessory.
 12. The audio accessory of claim 8, wherein the one or more processors are further configured to initiate playing a previous audio message when the slide of the button to the actuated position is received by the input device and there is no additional next audio message.
 13. The audio accessory of claim 8, wherein the one or more processors are in communication with a memory of a client computing device, the memory storing one or more of the audio updates and audio messages that are configured to be played using the audio accessory.
 14. An audio accessory comprising: a pair of earphones, each earphone having an outer surface, an inner surface opposite the outer surface, and a sidewall connecting the outer surface and the inner surface; an input device including a button, the button and two touch sensors on opposite sides of the input device, the two touch sensors being positioned to either side of the button; and one or more processors operatively coupled to the pair of earphones and the input device, the one or more processors being configured to: initiate an action when a click of the button is received by the input device; provide audio updates when a double-click of the button is received by the input device; prepare the input device to receive audio input when a prolonged click of the button is received; silence a currently playing audio message and initiate playing a next audio message through the pair of earphones when tactile input is received at the two touch sensors of the input device; and silence the currently playing audio message and mark the currently playing audio message for no further playback when prolonged tactile input is received at the two touch sensors by the input device.
 15. The audio accessory of claim 14, wherein: the input device includes a second button; and the one or more processors is configured to initiate playing a next audio message when a click of the second button is received by the input device.
 16. The audio accessory of claim 15, wherein: the input device includes a third button; and the one or more processors is configured to initiate playing a previous audio message when a click of the third button is received by the input device.
 17. The audio accessory of claim 14, wherein when the click of the button is received after an audio message suggesting a given action has been played through the pair of earphones, the initiated action is the given action.
 18. The audio accessory of claim 14, wherein the provided audio updates are based on one or more of time of day, location, and a user preference.
 19. The audio accessory of claim 14, wherein the one or more processors are configured to prepare the input device to receive audio input by activating a microphone of the audio accessory.
 20. The audio accessory of claim 14, wherein the one or more processors are further configured to initiate playing a previous audio message when the slide of the button to the actuated position is received by the input device and there is no additional next audio message. 